<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml">
 <head>
  <meta content="Copyright &copy; 2023 Thales. All Rights Reserved." name="copyright"/>
  <meta content="text/html;charset=utf-8" http-equiv="content-type"/>
  <meta content="text/css" http-equiv="Content-Style-Type"/>
  <title>
   Arcadia Reference - From System to Sub-systems, SW, HW
  </title>
  <link href="../../scripts/jquery-treeview/jquery.treeview.css" rel="stylesheet"/>
  <script src="../../scripts/jquery-treeview/lib/jquery-1.11.1.js" type="text/javascript">
  </script>
  <script src="../../scripts/jquery-treeview/jquery.treeview.js" type="text/javascript">
  </script>
  <link href="../../css/simpletree.css" rel="stylesheet" type="text/css"/>
  <link href="../../css/content.css" media="screen, projection" rel="stylesheet" title="default" type="text/css"/>
  <style>
   body {}
			.treeview {
				background-color: white ;
			}
	
			.treeview ul{ /*CSS for Simple Tree Menu*/
				background-color: white;
				font-size: 12px;
			}
	
			.treeview li{ /*Style for LI elements in general (excludes an LI that contains sub lists)*/
				background-color: white;
			}
  </style>
 </head>
 <body>
  <img src="../icon/logo_arcadia_small.png" style="float:left;width:50px;height:50px;"/>
  <nav>
   <a href="1a79525b3b624a7094acd0b580842ce6.html#">
    ARCADIA
   </a>
   <a href="1a79525b3b624a7094acd0b580842ce6.html#landscape">
    Engineering Landscape
   </a>
   <a href="1a79525b3b624a7094acd0b580842ce6.html#userGuide">
    User Guide
   </a>
   <a href="1a79525b3b624a7094acd0b580842ce6.html#reference">
    Reference Manual
   </a>
  </nav>
  <p>
   <br/>
  </p>
  <div id="content">
   <img alt="FunctionalChain" src="../icon/FunctionalChain.png" style="float:left; margin-right:10px"/>
   <h1>
    <a href="../ARCADIA/a47f60ce42d044d1933b6032e82c0a8d.html">
     From System to Sub-systems, SW, HW
    </a>
   </h1>
   <p style="margin-top:3px; margin-bottom:3px">
    <span class="elementMetaClass">
     Engineering Process
    </span>
    <p>
    </p>
   </p>
   <em class="elementPath">
    <a href="../ARCADIA/ad8c8a109fa64f039584c15108639254.html">
     Engineering Capabilities
    </a>
    &gt;
    <a href="../ARCADIA/4e8472cf52d44160a41ed722c73b1861.html">
     Support  Collaboration in Engineering
    </a>
    &gt;
    <a href="../ARCADIA/a47f60ce42d044d1933b6032e82c0a8d.html">
     From System to Sub-systems, SW, HW
    </a>
   </em>
   <p>
    <p>
     <strong>
      Challenge: How to specify expectations on sub-systems, software (SW) and hardware (HW) to contribute to the solution development and building
     </strong>
     .
    </p>
    <ul>
     <li>
      Build the solution architecture in co-engineering between system, sub-systems/SW/HW teams, and specialities/disciplines.
     </li>
     <li>
      Once a consensus is built, and its hypotheses checked by all stakeholders, extract the specification of each sub-system/SW/HW part from the solution architecture
     </li>
     <li>
      Define the contribution of each part and team to IVV strategy and test cases the same way, and add IVV expectations to the parts specification
     </li>
    </ul>
   </p>
   <h2>
    Related Diagrams
   </h2>
   <div>
    <p class="diagram-name" id="_0qjoMJRUEeqxb5_tqwKmHg">
     5  From System to Subsystems SW HW
    </p>
    <p class="diagram">
     <img alt="5  From System to Subsystems SW HW" src="a47f60ce42d044d1933b6032e82c0a8d/_0qjoMJRUEeqxb5_tqwKmHg.jpg" usemap="#5  From System to Subsystems SW HW__0qjoMJRUEeqxb5_tqwKmHg_PositionMap"/>
     <br/>
     <br/>
     <map name="5  From System to Subsystems SW HW__0qjoMJRUEeqxb5_tqwKmHg_PositionMap">
      <area alt="0f400333e4604c16a797eb161de26e50" coords="550,100,650,150" group="0f400333e4604c16a797eb161de26e50" href="../ARCADIA/0f400333e4604c16a797eb161de26e50.html#id0f400333-e460-4c16-a797-eb161de26e50" shape="rect"/>
      <area alt="e8a6129c560e4e5699f785edb67049e9" coords="550,10,650,60" group="e8a6129c560e4e5699f785edb67049e9" href="../ARCADIA/e8a6129c560e4e5699f785edb67049e9.html#ide8a6129c-560e-4e56-99f7-85edb67049e9" shape="rect"/>
      <area alt="b4f96ce88e5d4a75a44982269ade639f" coords="550,190,650,240" group="b4f96ce88e5d4a75a44982269ade639f" href="../ARCADIA/b4f96ce88e5d4a75a44982269ade639f.html#idb4f96ce8-8e5d-4a75-a449-82269ade639f" shape="rect"/>
      <area alt="21963be2f5f544798045079ed00879fa" coords="220,50,361,101" group="21963be2f5f544798045079ed00879fa" href="../ARCADIA/21963be2f5f544798045079ed00879fa.html#id21963be2-f5f5-4479-8045-079ed00879fa" shape="rect"/>
      <area alt="38c7424f5c11476490db367b0b43bc42" coords="10,100,110,150" group="38c7424f5c11476490db367b0b43bc42" href="../ARCADIA/38c7424f5c11476490db367b0b43bc42.html#id38c7424f-5c11-4764-90db-367b0b43bc42" shape="rect"/>
      <area alt="d260034d335e47c98fbec6f97f023fa3" coords="220,158,361,208" group="d260034d335e47c98fbec6f97f023fa3" href="../ARCADIA/d260034d335e47c98fbec6f97f023fa3.html#idd260034d-335e-47c9-8fbe-c6f97f023fa3" shape="rect"/>
     </map>
    </p>
    <p class="diagram-description">
     <p>
      This figure describes
     </p>
     <p>
      <strong>
       How to specify expectations on sub-systems, software (SW) and hardware (HW) to contribute to the solution development and building
      </strong>
      .
     </p>
     <ul>
      <li>
       Build the solution architecture in co-engineering between system, sub-systems/SW/HW teams, and specialities/disciplines.
      </li>
      <li>
       Once a consensus is built, and its hypotheses checked by all stakeholders, extract the specification of each sub-system/SW/HW part from the solution architecture
      </li>
      <li>
       Define the contribution of each part and team to IVV strategy and test cases the same way, and add IVV expectations to the parts specification
      </li>
     </ul>
     <p>
      For each step of this process, involving an engineering task or activity, the description gives some hints and methological recommendations. These recommendations are complementary with the description of the involved activity per se, in the context of the engineering concern and the process.
     </p>
    </p>
   </div>
   <h2>
    Contribution of each engineering activity to this process
   </h2>
   <table>
    <tr>
     <th>
      Engineering activity
     </th>
     <th>
      Specifics of activity for this process
     </th>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/38c7424f5c11476490db367b0b43bc42.html">
       Design PHYSICAL ARCHITECTURE
      </a>
     </td>
     <td>
      <p>
       The solution architecture design results in the definition and description of components, their functional contents and behaviour, their interfaces, allocated functional chains and scenarios, resources, etc. plus textual requirements describing or complementing them.
      </p>
      <p>
       This is the main input to defining the need of each sub-system, SW or HW item, as a (set of) component(s).
      </p>
     </td>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/21963be2f5f544798045079ed00879fa.html">
       Define &amp; enforce a PBS and Component Integration Contract
      </a>
     </td>
     <td>
      <p>
       As mentioned in 'Design Solution Architecture',the specification contract of each sub-system, software or hardware item is mostly extracted from the system architecture : description of components, their functional contents and behaviour, their interfaces, allocated functional chains and scenarios, resources, etc. plus textual requirements describing or complementing them.
      </p>
      <p style="margin: 3pt 0cm;">
       <span lang="EN-GB">
        <font color="#000000" size="2">
         This&nbsp;is a contribution to EPBS (End-Product Breakdown Structure) building, taking benefits from the former architectural work, to enforce components requirements definition, and prepare a secured IVVQ.
        </font>
       </span>
      </p>
      <p style="margin: 3pt 0cm;">
       <span lang="EN-GB">
        <font color="#000000" size="2">
         All choices associated to the system/SW chosen architecture, and all hypothesis and constraints imposed to components and architecture to fit need and constraints, are summarised and checked here.
        </font>
       </span>
      </p>
      <p style="margin: 3pt 0cm;">
       <font size="2">
        <font color="#000000">
         <i>
          <u>
           <span lang="EN-GB">
            Outputs
           </span>
          </u>
         </i>
         <span lang="EN-GB">
          from this step are mainly &ldquo;component Integration contract&rdquo; collecting all necessary expected properties for each component to be developed, and building &amp; IVVQ Strategy.
         </span>
        </font>
       </font>
      </p>
     </td>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/d260034d335e47c98fbec6f97f023fa3.html">
       Define a Components IVVQ Strategy
      </a>
     </td>
     <td>
      <p>
       The definition of the system-level IVV Strategy usually includes delegating part of verifications to sub-systems, when appropriate and confinable into&nbsp;one (possibly more) of&nbsp;them. The specification of delegated tests and verifications uses mainly allocation of all or parts of system-level functional chains and scenarios to sub-systems.
      </p>
     </td>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/e8a6129c560e4e5699f785edb67049e9.html">
       Perform HW &amp; mechanical engineering
      </a>
     </td>
     <td>
      <p>
       Hardware and mechanical engineering initial tasks (such as need analysis, general architecture, integration and verification policy, etc.) may be similar to the system-level one, properly adapted, tuned and taylored.
      </p>
     </td>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/0f400333e4604c16a797eb161de26e50.html">
       Perform SW engineering
      </a>
     </td>
     <td>
      <p>
       Software engineering structuring tasks (such as need analysis, general architecture, integration and verification policy, etc.) may be similar to the system-level one, properly adapted, tuned and taylored.
      </p>
      <p>
       Specific software-related issues such as agile practices can also benefit from the system approach. See 'Agility in engineering course'.
      </p>
     </td>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/b4f96ce88e5d4a75a44982269ade639f.html">
       Perform Sub-System Engineering
      </a>
     </td>
     <td>
      <p>
       Sub-system&nbsp;engineering structuring tasks (such as need analysis, general architecture, integration and verification policy, etc.) may be similar to the system-level one, properly adapted, tuned and taylored.
      </p>
     </td>
    </tr>
   </table>
   <h2>
    Diagrams displaying "From System to Sub-systems, SW, HW"
   </h2>
   <ul>
    <li>
     <a href="../ARCADIA/a47f60ce42d044d1933b6032e82c0a8d.html#_0qjoMJRUEeqxb5_tqwKmHg">
      5 - From System to Sub-systems, SW, HW*
     </a>
    </li>
   </ul>
  </div>
 </body>
</html>
